翻訳と辞書
Words near each other
・ Webster v. New Lenox School District
・ Webster v. Reproductive Health Services
・ Webster Wagner
・ Webster Wagner House
・ WebSite X5 Incomedia
・ WebSitePro
・ Websites and phone numbers in the Year Zero alternate reality game
・ Websites blocked in Belgium
・ Websites blocked in India
・ Websites blocked in mainland China
・ Websites blocked in Pakistan
・ WebSocket
・ WebSphere Application Server for z/OS
・ WebSphere Commerce
・ WebSphere Integration Developer
WebSphere Optimized Local Adapters
・ WebSphere Portal
・ Webstar
・ WebstaurantStore
・ Webster
・ Webster (CDP), Massachusetts
・ Webster (CTA station)
・ Webster (surname)
・ Webster (TV series)
・ Webster (village), New York
・ Webster A. Young
・ Webster Aitken
・ Webster Anderson
・ Webster Avenue
・ Webster B. Todd


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

WebSphere Optimized Local Adapters : ウィキペディア英語版
WebSphere Optimized Local Adapters
IBM WebSphere Optimized Local Adapters (OLA or WOLA) is a functional component of IBM's WebSphere Application Server for z/OS that provides an efficient cross-memory mechanism for calls both inbound to WAS z/OS and outbound from z/OS. Because it avoids the overhead of other communication mechanisms, it is capable of high volume exchange of messages. WOLA is an extension to the existing cross-memory exchange mechanism of WAS z/OS, with WOLA providing an external interface so z/OS address spaces outside the WAS z/OS server may participate in cross-memory exchanges. WOLA supports connectivity between a WAS z/OS server and one or more of the following: CICS, IMS, Batch, UNIX Systems Services and ALCS. WOLA was first made available in WAS z/OS Version 7, Fixpack 4 (7.0.0.4). Functional enhancements have appeared in subsequent fixpacks as documented in this article.
== History ==

The WebSphere Optimized Local Adapters for WAS z/OS (WOLA or OLA for short) has its origins in a desire to provide an efficient ''inbound'' calling mechanism; that is, from ''outside'' the Java EE environment into it to exercise Java EE assets. This requirement was particularly pronounced on z/OS where traditional batch processing sought the use of a growing base of programming assets based on Java EE and EJB technology.
Other inbound solutions existed, for example:
*Messaging, such as Websphere MQ or other JMS providers.
*RMI/IIOP
*Web Services
While each had its respective strengths; each also had its particular shortcomings: overhead and latency; difficulty in construction; or deficiencies in the security or transaction propagation model.
This was the original design point for the Optimized Local Adapters. The architects of the solution extended the design to include bi-directional invocations: ''inbound'' to WAS z/OS from an external address space, and ''outbound'' from WAS to an external address space.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「WebSphere Optimized Local Adapters」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.